home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d19
/
dldoor17.arc
/
DLDOOR.DOC
next >
Wrap
Text File
|
1989-06-17
|
10KB
|
250 lines
DLDoor Version 1.17ß
(C)opyright 1989 by Doug Laine
2049 Chestnut Street #6, Philadelphia
The Philly Exchange (215) 563-8109
Latest Changes
--------------
1.17 -- Added three minute screen blanking
Corrected NEWS checking. Was missing the configuration of
showing the news all the time or when new.
Fixed bug with the keyboard timeout. Was not timing out.
FINALLY got monochrome worked out. Check for /MONO command
1.16 -- Made to work automatically with /D version of PCBoard.
Added multiple event capability
1.15 -- Added configuration file to select doors based on user levels
DLDoor Version 1.17
---------------------
I appoligize for the very basic documentation, but I have not had alot
of time to devote to it! There will be more complete documentation as
soon as I get the program finished.
Some of the other programs that I will be working on, will be
replacements to all the utilities that you currently use with PCBoard
(R). They will make it so that ProDoor can be used totally as a stand
alone board.
Installation
------------
This program has only been tested with ProDoor 3.0ß and has been
working rather well. To install this program, all you will have to do
is to replace PCBOARD in your board batch file with DLDOOR!
One advantage of using this as a front end, is that, door calls from
ProDoor will automatically return you to ProDoor!
Configuration
-------------
If you are running under a true network, start DLDoor as:
DLDOOR /NETWORK Disables the multitasking on a network system
DLDOOR /NOTASKER Tells DLDoor that you are not running taskers
use only if DLDoor doesn't auto configure
DLDOOR /MONO Makes the ANSI colors compatible with Mono, and
get rid of the underline mess. Should check auto-
matically in the next few versions.
Version 1.16ß4 and above will now auto-configure to the /D version of
PCboard(r)
Misc. Information
-----------------
The Support board : 215 -563-8109 (MNP5) or 215 -563-8137 (HST)
Conference number 3
Address : Doug Laine, C/O DLDoor ersion 1.17ß
2049 Chestnut Street #6
Philadelphia, PA 19103
Cost: $25.00 / Shareware. Try it, you like, you pay!
Using PCBoard(r) with DLDoor
----------------------------
It is possible to use PCBoard with DLDoor! You will basically set up
PCBoard as a door to the system.
First use PCBsetup(r) to configure your system. You will need to
select Options #1. This will display a number of selections, one of
them being, Exit to DOS after each call. You must be sure that this is
set to yes. Failure to do so, will cause PCBoard(r) to be reloaded
when a user logs of from inside PCBoard(r) instead of DLDoor.
Now, using the documentation that comes with PCBoard(r), setup the rest
of the system, as though you were creating any other door. For an
example, call the door PCBOARD. Here is a very simple file that will
do the trick. This is the one that I use on my system:
PCBOARD:
echo off
pcboard
board
By setting the file up this way, you have created a Door toggle. In
other words, wherever you call it from, you will be returned simply by
calling that door again.
The only reason that that may not happen, would be if you have used the
configuration file, and your user level sends you to another door.
The main advantage of setting this up like this, is that it will give
you all your Sysop commands back. Until they can be re-written, this
should help you get by.
DLDoor Configuration File
-------------------------
Version 1.15ß started the implimentation of a door default file. This
file simply contains information about each userlevel that you have, or
want to include in this file and a specific door that you would like to
have that userlevel load.
On thing to remember when doing this, is that if a door does not exit
out, it will not allow the user to return to the main system. Also, if
the users userlevel is not changed in the user file, then the user will
end up stuck in that door also.
The main reason for something like this function, is to maybe send a
new user to a validation door of some sort. This door must then update
there user level, and then when they exit the door, DLDoor will again
check their new user level and then load the appropriate door.
If no configuration file is found, then the system will default to
ProDoor(r). Also, should a user level not be specified, the same will
happen.
First off, the configuration file must be in the default directory, and
must be called DLDOOR.CFG. There are three columns in the file and
they are as follows:
User level,Door batch file,Description to show user while loading
User level
This is the userlevel that you want to select
Door batch file
This is the door file that PCboard(r) uses in a standard
configuration
Description
This is a comment field used to display to a user while the door is
being loading. The system will provide : "Loading " (your
description) "! Please wait."
Example:
110,PCBOARD,PCboard for the Sysop
This will send a user with the level 110 into the Door PCBOARD and
print PCBoard for the Sysop in the Loading prompt.
Multiple Event Control
----------------------
DLDoor now provides a way to get around the one event limitation of
PCBoard. You can have as many events per day as you want.
Once again, configuration is reletively easy.
You must create a file called DLDOOR.EVT which will contain all the
event information. Here is the format of the file:
Event time,Weekday numbers,Batch file,Event slide
Event time
This is the time that the event will run. The format should be in a
24 hour format and be HH:MM.
Weekdays number
This is the list of all the days that you would like to have this
batch file run. Valid number are 0 through 6, with 0 being sunday
and 6 being saturday. For example, should you want your batch to
run only on monday and thursday, you would place 14 as the weekday
numbers.
Batch file
This is the name of the event file that you would like to run at the
selected time and day. Be sure to include the extention of the
filename.
Event slide
This is a YES or NO. Currently this is not implimented, but you
must include this as it will be implimented very soon. When it is,
you will be able to select the ability to slide and event or not.
Example:
01:00,124,CALLPBS.SYS,NO
This would cause the event CALLPBS.SYS to be executed at 01:00 on
Sunday, Tuesday and Thursday, and don't slide the event time.
Legal Stuff
-----------
LIMITED WARRANTY
DOUG LAINE DOES NOT WARRANT THAT THE PROGRAM WILL MEET YOUR
REQUIREMENTS OR THAT THE OPERATION OF THE PROGRAM WILL BE UNINTERRUPTED
AND ERROR FREE. YOU ARE SOLELY RESPONSIBLE FOR THE SELECTION OF THE
PROGRAM TO ACHIEVE YOUR INTENDED RESULTS AND FOR THE RESULTS ACTUALLY
OBTAINED.
DISCLAIMER
The author has taken due care in the preparation of this document and
the associated program. Insofar as specific mention of program
features, the author believes the information to be true. No warranty
is made regarding the suitability of the program to be compatible with
your computer. Incidental and consequential damages caused by
malfunction, defect, or otherwise are not the responsibility of Doug
Laine, and to the extent permitted by law, and hereby excluded both for
the property and, to the extent not unconscionable, for personal injury
damage. (Some states or jurisdictions do not allow the exclusion or
limitation of incidental or consequential damages, so the above
limitation or exclusion may not apply to you.)
Doug Laine also reserves the right to make amendments to the contents
of this document from time to time, to reflect changes made to the
specification of the DLDoor system or for any other reason.